Mobile device inactive mode and inactive mode verification

ABSTRACT

A mobile device, comprising: a processor; and a memory including instructions that when executed by the processor cause it to perform the steps of: receiving a user selection to automatically enter an inactive mode in response to an action within the mobile device indicating the device is being used in a moving vehicle; receiving a communication from a wireless communication module; if the mobile device is not in inactive mode, providing a notification to the user that a communication has been received; if the mobile device is in inactive mode, transmitting an away message via the wireless module.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application incorporates by reference and claims priority to U.S.Non-provisional application Ser. No. 14/176,107 filed Feb. 9, 2014 andto U.S. Provisional Application No. 61/835,234 filed Jun. 14, 2013.

BACKGROUND OF THE INVENTION

The present subject matter relates generally to a mobile deviceincluding functionality for suppressing user notifications ofcommunications received by the mobile device and notifying the sender ofthe communication that the user is not receiving communications.Further, the present subject matter relates generally to systems andmethods for verifying that a user was not receiving communicationsduring a particular period of time.

User distraction caused by mobile devices has become a serious problemin modern society. For example, motor vehicle accidents caused bydistracted driving are on the rise and have become as serious as drivingwhile intoxicated. Many drivers are aware of the risks of distracteddriving but may lack the resolve to avoid trying to respond to incomingcommunications. One previous solution was to power down the mobiledevice while driving, however, this is inconvenient and easy to forgetto initiate. Further, powering down the device may block access tourgent communications that may need to be received. What are needed aremechanisms to limit user communication distractions without forcing theuser to power down a mobile device and miss essential communications.

Further, the proliferation of accidents cause by distracted driving hascreated a need to prove that one was not operating a communicationsdevice during operation of a vehicle. What are needed are mechanisms toshow that a user was not using a communications device during anaccident while operating a vehicle.

Accordingly, there is a need for a mobile device including functionalityfor suppressing communications to a user and systems for verifying thata user was not receiving communications during a particular period oftime, as described herein.

BRIEF SUMMARY OF THE INVENTION

To meet the needs described above and others, the present disclosureprovides a mobile device including functionality for suppressingcommunications to a user and systems for verifying that a user was notreceiving communications during a particular period of time.

As used herein, a communication may include a mobile device call, SMStext message, email, application notification, etc. A sender includes anindividual sending the communication.

An inactive mode for a mobile device as disclosed herein may beimplemented using stored instructions that implement the functionalitydisclosed herein. In a preferred embodiment, the stored instructions maybe provided in the form of a mobile device application. A user mayinstall the mobile device application through a mobile deviceapplication online store.

A user may enable an inactive mode of the device to suppressnotification of incoming phone calls, text, emails, etc. andautomatically notify the sender with an away message. By suppressing thecommunications distracted driving may be reduced. One drawback, however,is that senders may feel upset that they are not being answered when thesender is expecting the user to reply. Thus, in order to reassuresenders that they will receive a response at the earliest convenientopportunity, the mobile device permits the user to send an away messageupon receipt of a communication.

Further, the device may communicate with a certification server to“certify” that a mobile device was not operational during a certainperiod as evidence that the phone was not used during driving. Byenabling a user to show that he or she did not use mobile device duringoperation of a vehicle, he or she may be able to qualify for discountsfrom an insurance company or may be able to show he or she was not atfault in an accident. Further, parents may use such records to verifythat teenage drivers are not being distracted by their mobile device.

In an embodiment, a method carried out by a mobile device to provide foran inactive mode and thus prevent distracted driving includes the stepsof: placing the mobile device in inactive mode; detecting one or moreincoming communications; suppressing notification of the user of the oneor more incoming communications; transmitting an away message to one ormore senders of the one or more communications; and notifying the userof missed communications upon completion of the inactive mode.

The method begins when the mobile device is placed in inactive mode. Theinactive mode may be activated by many different mechanisms. Forexample, a user may press a button to begin the inactive mode.Alternatively, a user may schedule a time period during which the mobiledevice is automatically in inactive mode. Even further, inactive modemay be automatically initiated upon the use of a driving directionsfunctionality of the mobile device. Yet even further, the inactive modemay be automatically initiated upon the pairing of the mobile device anda vehicle. Moreover, inactive mode may be activated by a remote user,for example, to enable parents to limit distracted driving by teenagers.Additionally, the inactive mode may be activated by the mobile devicedetecting a particular location using GPS, such as a gym or school,where inactive mode is routinely activated. It is contemplated that anyinput that indicates that the user is not to be distracted may be usedto place the device in inactive mode, as will be understood by those ofskill in the art.

While in inactive mode, the mobile device will detect incomingcommunications. When inactive mode functionality is provided as a mobileapplication, the mobile application may register with the operatingsystem of the mobile device to receive a notification upon acommunication event, such as a mobile call, SMS message, or email. Uponreceipt of notification of the incoming communication, the mobileapplication may capture contact information of the sender, such as phonenumber or email address.

In addition to suppressing communications, inactive mode may restrictthe user's use of the mobile device. For example, the user of the mobiledevice may be restricted from accessing a web browser on the mobiledevice. Inactive mode may restrict all use of the mobile device or maypermit only selective access to needed functionality. For example, whendriving, mapping and navigation functionality may remain accessible.

It is contemplated that the user may customize the allowed functionalityduring inactive mode. Alternatively or additionally, the restriction onthe functionality may be pre-programmed in the device, for example, ifthe inactive mode functionality is embodied in a mobile applicationdistributed by an insurance company, the restriction of functionalitymay be optimized to minimize distracted driving accidents. Further, aremote user may restrict the functionality of the device. For example, aparent may limit a child's use of a mobile device during nighttimesleeping hours.

Upon receiving notification of a communication event, the mobile devicemay suppress normal user notification. The mobile device may suppressnormal user notification actions, such as ringing, vibration, and screenactivation. Further the mobile device may suppress applications normallylaunched upon a communication event, such as a mobile call application.In some embodiments, the mobile device may permit normal usernotification if the sender is on a pre-screened list of allowed senders.

After suppressing user notification, the mobile device may transmit anaway message to the sender. The away message may be sent via the samemedium that the original communication was made in. For example, if atext message was received, the mobile device may transmit a response viatext message. Alternatively, the message may be sent by a differentmedium. For example, if a phone call was received, the mobile device maytransmit the away message via text message or email (if, for example,the sender has an associated email address in the users contacts). It isfurther contemplated that the user's inactive mode away message may beautomatically shared to social networks such Facebook and Twitter uponactivation of the inactive mode.

The user may configure an away message before placing the mobile devicein inactive mode. The user may configure multiple away messages andchoose among the away messages when placing the mobile device in awaymode.

At the appropriate time, the device may leave inactive mode and permitthe user to use the full functionality of the device. In an embodiment,inactive mode may be disabled by pressing a button ending inactive mode.Alternatively, where inactive mode was scheduled to start automatically,the mobile device may leave inactive mode by reaching the end of ascheduled time. Further, where the mobile device was placed in inactivemode by the driving directions functionality, the mobile device mayleave inactive mode by arriving at a destination. Even further, wherethe mobile device was placed in inactive mode remotely, the mobiledevice may be removed from inactive mode by remote deactivation, etc. Itwill be apparent to one of skill in the art that that the mobile devicemay be removed from inactive mode by any mechanism that reflects thatthe need for restricted access is no longer needed.

Upon completion of the inactive mode, the mobile device notifies user ofmissed communications. The user may then view any text messages oremails, or may listen to voicemails left by the sender.

As described, the device may “certify” or prove that a mobile device wasnot operational during a certain period as evidence that the phone wasnot used during driving. A method of proving a cell phone was disabledcomprises the steps of: receiving an input by the mobile device to beginthe inactive mode; transmitting an inactive mode begin notification fromthe mobile device to the certification server; receiving, by thecertification server, an inactive mode begin notification; suppressingnotifications to a user; receiving an input by the mobile device to endthe inactive mode; transmitting an inactive mode end notification fromthe mobile device to the certification server; receiving an inactivemode end notification by the certification server; generating, by thecertification server, a certified record of the time of the inactivemode begin notification and the inactive mode end notification.

The method of proving a cell phone was disabled may begin upon themobile device being placed in inactive mode. As previously described,the mobile device may be placed in inactive mode by the user pressing abutton to begin the inactive mode; by the user scheduling a time periodduring which the mobile device is automatically in inactive mode; by theuse of the driving directions functionality of the mobile device; byactivation by a remote user; etc.

Upon being placed in inactive mode, the mobile device may transmit aninactive mode begin notification to the server. The inactive mode beginnotification may include a user identifier, and a begin timestampindicating the time that the inactive mode was initiated. Further, theinactive mode begin notification may include a listing of functionalitypermissions to record the functionality made available and/or thefunctionality made restricted to the user during the inactive mode. Itis contemplated that the mobile device need not immediately transmit theinactive mode begin notification upon the step of receiving an input tobegin inactive mode is received, and the mobile device may alternativelytransmit the inactive mode begin notification when requested, when aconnection is available, during periods of low bandwidth utilization, orany other time useful to create the certification.

The certification server receives the inactive mode begin notificationfrom the mobile device. The certification server may assume thatinactive mode is operating continuously until receiving a signal, suchas an inactive mode end notification, that inactive mode has beendisabled. A certified record of the data contained in the inactive modebegin notification may be created and stored in a database of thecertification server. The certified record may include a first timestampof the time the inactive mode begin notification was received.

In inactive mode, the mobile device may suppress communications andenforce the restrictions of the inactive mode until the step ofreceiving an input to end inactive mode. As previously described, aninput may be the user pressing a button to end the inactive mode, theuser scheduling a time period during which the mobile device isautomatically in inactive mode, the use of the driving directionsfunctionality of the mobile device, activation by a remote user; etc.

At the conclusion of inactive mode, the mobile device may transmit aninactive mode end notification to the certification server to indicatethat the device has left the inactive mode. The inactive mode endnotification may include a user identifier and a end timestamp markingthe time that the mobile device was removed from inactive mode. Further,the inactive mode end notification may include a listing offunctionality permissions to record the functionality made availableand/or the functionality made restricted to the user during the inactivemode. It is contemplated that the mobile device need not immediatelytransmit the inactive mode end notification upon the step of receivingan input to begin inactive mode is received, and the mobile device maytransmit the inactive mode end notification when requested, when aconnection is available, during periods of low bandwidth utilization, orany other time useful to create the certification.

The certification server may receive an inactive mode end notificationfrom the mobile device. Upon receipt of the inactive mode endnotification, the certification server may make a certified record ofthe inactive mode session. The certified record of the inactive modesession may include the inactive mode begin notification, an inactivemode begin notification arrival timestamp recording the arrival of theinactive mode begin notification, the inactive mode end notification,and an inactive mode end notification arrival timestamp recording thearrival of the inactive mode end notification. The record may be used toverify that the inactive mode was enabled during a period of time. To doso, the record may be made available via a user interface to the user,an insurance company, the police, the courts, a parent of the user,etc., to certify the times the device was in inactive mode and therestrictions on functionality in place during inactive mode.

In an embodiment, a mobile device includes: a processor; and a memoryincluding instructions that when executed by the processor cause it toperform the steps of: receiving a user selection to automatically enteran inactive mode in response to an action within the mobile deviceindicating the device is being used in a moving vehicle; receiving acommunication from a wireless communication module; if the mobile deviceis not in inactive mode, providing a notification to the user that acommunication has been received; and if the mobile device is in inactivemode, transmitting an away message via the wireless module.

In some embodiments of the mobile device, the action is the activationof a driving directions functionality. In other embodiments, the actionis GPS location functionality detecting a velocity above a certain rate.In additional embodiments, the action is pairing the mobile device withthe moving vehicle.

In some embodiments of the mobile device, the communication is a mobilephone call. In other embodiments, the away message is one of a mobilephone call, an SMS message, or an email. In additional embodiments thecommunication is an SMS phone call. In further embodiments, thecommunication is an email.

In some embodiments of the mobile device, the memory further includesinstructions that when executed by the processor cause it to perform thesteps of: receiving an input from a user requesting access to a functionof the mobile device; if the mobile device is not in inactive mode,providing access to the requested functionality; and if the mobiledevice is in inactive mode, checking if the requested functionality ispresent on a list of restricted functionality, and if the requestedfunctionality is present on a list of restricted functionality, refusingaccess to the requested functionality.

One objective of the invention is to increase driver safety by reducingmobile device communications as a source of distraction.

A further objective is to inform callers of the delay and the reason forfailing to respond.

Another objective of the invention is to provide a mechanism for usersto prove that the communication functions of their mobile device weredisabled at a particular time.

Additional objects, advantages and novel features of the examples willbe set forth in part in the description which follows, and in part willbecome apparent to those skilled in the art upon examination of thefollowing description and the accompanying drawings or may be learned byproduction or operation of the examples. The objects and advantages ofthe concepts may be realized and attained by means of the methodologies,instrumentalities and combinations particularly pointed out in theappended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present concepts, by way of example only, not by way of limitations.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 is a schematic view of the ecosystem of a device includingfunctionality for suppressing communications to a user using an inactivemode and a verification system to verify that a user was not receivingcommunications during a particular period of time.

FIG. 2 is a diagram of an example of a device including functionalityfor suppressing communications to a user using an inactive mode andverifying that a user was not receiving communications during aparticular period of time.

FIG. 3 is a flow chart illustrating a method carried out by a mobiledevice to provide for an inactive mode.

FIG. 4 a is an example mobile device user interface showing a startscreen used to begin the inactive mode.

FIG. 4 b is an example mobile device user interface showing a schedulingscreen to schedule a time period during which the mobile device isautomatically in inactive mode.

FIG. 4 c is an example mobile device user interface showing aGPS/directions screen that when opened may trigger the inactive mode.

FIG. 4 d is a front view of a mobile device user interface showing aBluetooth device detection screen that when used to accept a Bluetoothconnection may trigger the inactive mode.

FIG. 5 a is an example mobile device user interface showing a custommessage selection screen.

FIG. 5 b is an example mobile device user interface showing a custommessage creation screen.

FIG. 5 c is an example mobile device user interface showing a custommessage selection screen including example away messages.

FIG. 5 d is an example mobile device user interface showing a startscreen that includes a custom away message.

FIG. 6 is an example mobile device user interface showing a notificationscreen displayed upon leaving inactive mode.

FIG. 7 is a flow chart illustrating a certification method to create acertified record at the certification server that a mobile device wasinactive during a particular time.

FIG. 8 a is a diagram of an example inactive mode begin notificationcreated during the execution of the certification method of FIG. 7.

FIG. 8 b is a diagram of an example inactive mode end notificationcreated during the execution of the certification method of FIG. 7.

FIG. 8 c is a diagram of an example record of an inactive mode sessioncreated during the execution of the certification method of FIG. 7.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates the ecosystem 10 of an example of a mobile device 100including functionality for suppressing communications using an inactivemode. As shown in FIG. 1, the ecosystem 10 includes a communicationsnetwork 40 which provides communications functionality to the mobiledevice 100, other communication devices 20 which other users may use tocommunicate to the mobile device 100, and a certification server 30 thatmay verify that a user 15 was not receiving communications during aparticular period of time.

A user 15 may enable an inactive mode of the device 100 to suppressnotification of incoming phone calls, text, emails, and othercommunications and automatically notify the device 20 of the sender 17with an away message. By suppressing the incoming communications, themobile device 100 may minimize user distractions permitting the user 15to maintain concentration on important tasks, such as driving. Onedrawback, however, is that senders 17 may feel upset that they are notbeing answered when the sender 17 is expecting the user 15 to answercommunications. Thus, in order to reassure senders 17 that theircommunication will receive a response at the earliest convenientopportunity, the mobile device 100 permits the user 15 to send an awaymessage upon receipt of a communication.

FIG. 2 is a block diagram of an example implementation of a mobiledevice 100 including an inactive mode. The mobile device 100 includescommunication functions that can be facilitated through one or morewireless communication subsystems 120, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 120 can depend on the communication network(s)over which the mobile device 100 is intended to operate. For example,the mobile device 100 can include communication subsystems 120 designedto operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fior WiMax network, and a Bluetooth network. In particular, the wirelesscommunication subsystems 120 may include hosting protocols such that themobile device 100 may be configured as a base station for other wirelessdevices.

A memory 138 may store communication instructions 142 to facilitatecommunicating with one or more additional devices, one or more computersand/or one or more servers. The memory 138 may include phoneinstructions 148 to facilitate phone-related processes and functions;short message service instructions 150 to facilitate SMS-messagingrelated processes and functions; electronic mail instructions 151 tofacilitate electronic-mail processes and functions. The phoneinstruction 148, the short message service instructions 150, electronicmail instructions 151 may include default instructions to notify a uservia sound, visual, or vibration cues to alert the user of incomingcommunications. The memory may further include inactive modeinstructions 147 to suppress the sound, visual, or vibrationcommunication cues and manage the inactive mode related processes andfunctions further described herein.

Turning to FIG. 3, in an embodiment, a method 300 carried out by amobile device 100 to provide for an inactive mode includes: the step 301of placing the mobile device 100 in inactive mode; the step 302 ofdetecting one or more incoming communications; the step 303 ofsuppressing notification of the user 15 of the one or more incomingcommunications; the step 304 of transmitting an away message to one ormore senders 17 of the one or more communications; and the step 305 ofnotifying the user 15 of missed communications upon completion of theinactive mode.

The method 300 begins at step 301 when the mobile device 100 is placedin inactive mode. Inactive mode may be activated by many differentmechanisms. For example, as shown in FIG. 4 a, a user 15 may press astart button 510 on a start screen 520 to begin the inactive mode.Alternatively, a user 15 may select the set timer button 515 on thestart screen 515 to enter a scheduling screen 530, as shown in FIG. 4 b,to schedule a time period during which the mobile device 100 isautomatically in inactive mode. Even further, as shown in FIG. 4 c, theinactive mode may be automatically initiated upon the opening of aGPS/directions screen 540 of the mobile device. Yet even further, asshown in FIG. 4 d, the inactive mode may be automatically initiated uponthe pairing of the mobile device 100 and a vehicle, as shown by theBluetooth device detection screen 550. Moreover, the inactive mode maybe activated by a remote user 15, for example, to enable parents tolimit distracted driving by teenagers. Additionally, the inactive modemay be activated by the mobile device 100 detecting a particularlocation using GPS, such as a gym or school, where inactive mode isroutinely activated. It is contemplated that any input that may indicatethat the user is not to be distracted may be used to place the device ininactive mode, as will be understood by those of skill in the art.

Once placed in inactive mode, at step 302, the mobile device 100 willdetect any incoming communications normally. When inactive modefunctionality is provided as a mobile application, upon enteringinactive mode the mobile application may register with the operatingsystem of the mobile device 100 to receive a notification upon acommunication event, such as a mobile call, SMS message, or email. Uponreceipt of notification of the incoming communication, the mobileapplication may capture contact information of the sender 17, such asphone number or email address.

Proceeding to step 303, upon receiving notification of an incomingcommunication, the mobile device 100 may suppress normal usernotification. The mobile device 100 may suppress normal usernotification actions, such as ringing, vibration, and screen activation.Further the mobile device 100 may suppress applications normallylaunched upon a communication event, such as a mobile call application.In some embodiments, the mobile device 100 may permit normal usernotification if the sender 17 is on a pre-screened list of allowedsenders 17.

After suppressing user notification of an incoming communication, themobile device 100, at step 304 of the method 300, may transmit an awaymessage 575 to the sender 17. The user 15 may configure multiple awaymessages 575 and choose among the away messages 575 when placing themobile device 100 in away mode. As shown in FIGS. 5 a-5 d, the user 15may configure an away message before placing the mobile device 100 ininactive mode. FIG. 5 a illustrates an away message selection screen 560before the user 15 has set up an away message 575. A user 15 may selectthe away message creation button 565 to enter an away message editingscreen 570 including an edit box 572, as shown in FIG. 5 b. Aftercreating away messages 575, the user 15 may select from the awaymessages 575 tin the away message selection screen 560 as shown in FIG.5 c. Upon selecting an away message 575, the start screen 520 is openedpermitting the user to start the inactive mode. It is furthercontemplated that the away message 575 may be automatically shared tosocial networks such Facebook and Twitter upon activation of theinactive mode.

In some embodiments, the away message 575 may be sent via the samecommunications medium in which the original communication was made. Forexample, if a text message was received, the mobile device 100 maytransmit the away message 575 via text message. Alternatively, the awaymessage 575 may be sent by a different communications medium. Forexample, if a phone call was received, the mobile device 100 maytransmit the away message 575 via text message or email.

Upon completion of the inactive mode, next at step 305, the mobiledevice 100 notifies the user 15 of missed communications. At the missedcommunications screen 580 shown in FIG. 6, the user 15 may then view anytext messages or emails by clicking the view message button 585, listento voicemails left by the sender 17 by clicking the view calls button587, or otherwise use the full functionality of the device. In anembodiment, inactive mode may be disabled by pressing a button endinginactive mode. Alternatively, where inactive mode was scheduled to startautomatically, the mobile device 100 may leave inactive mode by reachingthe end of a scheduled time. Further, where the mobile device 100 wasplaced in inactive mode by the driving directions functionality, themobile device 100 may leave inactive mode by arriving at a destination.Even further, where the mobile device 100 was placed in inactive moderemotely, the mobile device 100 may be removed from inactive mode byremote deactivation. It will be apparent to one of skill in the art thatthat the mobile device 100 may be removed from inactive mode by anymechanism that reflects that the need for restricted access is no longerneeded.

In addition to suppressing communications, inactive mode may restrictthe user's use of the mobile device. For example, the user 15 of themobile device 100 may be restricted from accessing a web browser,applications, communications programs, etc. Inactive mode may restrictall use of the mobile device 100 or may permit only selective access tocertain functionality. For example, when driving, mapping andGPS/navigation functionality may remain accessible.

It is contemplated that the user 15 may customize the allowedfunctionality during inactive mode. Alternatively or additionally, therestriction on the functionality may be pre-programmed in the inactivemode instructions 147. For example, if the inactive mode functionalityof the mobile device 100 is embodied in a mobile application distributedby an insurance company, the restriction of functionality may beoptimized to minimize distracted driving accidents. Further, a remoteuser may restrict the functionality of the mobile device 100. Forexample, a parent may limit a child's use of a mobile device 100 duringnighttime sleeping hours.

Referring to FIG. 4, the certification method 400 may be used to createa certified record 670 (FIG. 6 c) by the certification server 30 thatrecords that a mobile device 100 was inactive during a particular time.As shown in FIG. 4, the certification method 400 includes: the step 401of receiving an input by the mobile device 100 to begin the inactivemode; the step 402 of transmitting an inactive mode begin notification610 from the mobile device 100 to the certification server 30; the step403 of receiving, by the certification server 30, an inactive mode beginnotification 610; the step 404 of suppressing notifications to a user15; the step 405 of receiving an input by the mobile device 100 to endthe inactive mode; the step 406 of transmitting an inactive mode endnotification 650 from the mobile device 100 to the certification server30; the step 407 of receiving an inactive mode end notification 650 bythe certification server 30; the step 408 of generating, by thecertification server 30, a certified record 670 of the time of theinactive mode begin notification 610 and the inactive mode endnotification 650.

The certification method 400 may begin upon the step 401 of the mobiledevice 100 receiving an input to begin the inactive mode. For example,as shown in FIG. 4 a, a user 15 may press a start button 510 on a startscreen 520 to begin the inactive mode. Alternatively, a user 15 mayselect the set timer button 515 on the start screen 515 to enter ascheduling screen 530, as shown in FIG. 4 b, to schedule a time periodduring which the mobile device 100 is automatically in inactive mode.Even further, as shown in FIG. 4 c, the inactive mode may beautomatically initiated upon the opening of a GPS/directions screen 540of the mobile device. Yet even further, as shown in FIG. 4 d, theinactive mode may be automatically initiated upon the pairing of themobile device 100 and a vehicle, as shown by the Bluetooth devicedetection screen 550. Moreover, the inactive mode may be activated by aremote user 15, for example, to enable parents to limit distracteddriving by teenagers. It is contemplated that any input that mayindicate that the user is not to be distracted may be used to place thedevice in inactive mode, as will be understood by those of skill in theart.

Upon being placed in inactive mode, at step 402 the mobile device 100may transmit an inactive mode begin notification 610 to thecertification server 30. As shown in FIG. 8 a, the inactive mode beginnotification 610 may include a user identifier 620, and a begintimestamp 630 indicating the time that the inactive mode was initiated.Further, the inactive mode begin notification 610 may include a listingof functionality permissions 640 to record the functionality madeavailable and/or the functionality made restricted to the user duringthe inactive mode. It is contemplated that the mobile device 100 neednot immediately transmit the inactive mode begin notification 610 uponthe step 401 of receiving an input to begin inactive mode is received,and the mobile device 100 may alternatively transmit the inactive modebegin notification 610 when requested, when a connection is available,during periods of low bandwidth utilization, or any other time useful tocreate the certification.

At step 403, the certification server 30 may receive an inactive modebegin notification 610. The certification server 30 may assume thatinactive mode is operating continuously until receiving a signal, suchas an inactive mode end notification 650 (FIG. 8 b), that inactive modehas been disabled. A certified record 670 of the data contained in theinactive mode begin notification 610 may be created and stored in adatabase of the certification server 30. As shown in FIG. 8 c, thecertified record 670 may include a first timestamp 680 of the time theinactive mode begin notification 610 was received.

At step 404, the mobile device 100 may suppress communications andenforce the restrictions of the inactive mode until the step 405 ofreceiving an input to end inactive mode. As previously described, aninput may be the user pressing a button to end the inactive mode, theuser scheduling a time period during which the mobile device 100 isautomatically in inactive mode, the use of the driving directionsfunctionality of the mobile device 100, activation by a remote user;etc.

At step 406, the mobile device 100 may transmit an inactive mode endnotification 650 to the certification server 30 to indicate that thedevice 100 has left the inactive mode. The inactive mode endnotification 650 may include a user identifier and a end timestamp 660marking the time that the mobile device was removed from inactive mode.Further, the inactive mode end notification 650 may include a listing offunctionality permissions 640 to record the functionality made availableand/or the functionality made restricted to the user 15 during theinactive mode. It is contemplated that the mobile device 100 need notimmediately transmit the inactive mode end notification 650 upon thestep 405 of receiving an input to begin inactive mode is received, andthe mobile device 100 may transmit the inactive mode end notification650 when requested, when a connection is available, during periods oflow bandwidth utilization, or any other time useful to create thecertification.

At step 407, the certification server 30 may receive an inactive modeend notification 650. Upon receipt of the inactive mode end notification650, the certification server 30 may make a certified record 670 of theinactive mode session. The certified record 670 of the inactive modesession may include the inactive mode begin notification 610, aninactive mode begin notification arrival timestamp 680 recording thearrival of the inactive mode begin notification 610, the inactive modeend notification 650, and an inactive mode end notification arrivaltimestamp 690 recording the arrival of the inactive mode endnotification 650. In some embodiments, the certified record 670 mayfurther include a GPS location trace of the mobile device 100 while themobile device was in inactive mode. By storing a GPS location trace inthe certified record, the user may, among other things, provide proof oflocation during inactive mode, as may be useful when an accident hasoccurred. The certified record 670 may be used to verify that theinactive mode was enabled during a period of time. To do so, the recordmay be made available via a user interface to the user 15, an insurancecompany, the police, the courts, a parent of the user 15, etc., tocertify the times the device was in inactive mode and the restrictionson functionality in place during inactive mode.

Referring back to FIG. 2, the mobile device 100 includes a memoryinterface 102, one or more data processors, image processors and/orcentral processors 104, and a peripherals interface 106. The memoryinterface 102, the one or more processors 104 and/or the peripheralsinterface 106 can be separate components or can be integrated in one ormore integrated circuits. The various components in the mobile device100 can be coupled by one or more communication buses or signal lines,as will be recognized by those skilled in the art.

Sensors, devices, and additional subsystems can be coupled to theperipherals interface 106 to facilitate various functionalities. Forexample, a motion sensor 108 (e.g., a gyroscope), a light sensor 110,and a positioning sensor 112 (e.g., GPS receiver) can be coupled to theperipherals interface 106 to facilitate the orientation, lighting, andpositioning functions described further herein. Other sensors 114 canalso be connected to the peripherals interface 106, such as a proximitysensor, a temperature sensor, a biometric sensor, or other sensingdevice, to facilitate related functionalities.

A camera subsystem 116 and an optical sensor 118 (e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor) can be utilized to facilitate camera functions, such asrecording photographs and video clips.

An audio subsystem 122 can be coupled to a speaker 124 and a microphone126 to facilitate voice-enabled functions, such as voice recognition,voice replication, digital recording, and telephony functions.

The I/O subsystem 128 can include a touch screen controller 130 and/orother input controller(s) 132. The touch-screen controller 130 can becoupled to a touch screen 134. The touch screen 134 and touch screencontroller 130 can, for example, detect contact and movement, or breakthereof, using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith the touch screen 134. The other input controller(s) 132 can becoupled to other input/control devices 136, such as one or more buttons,rocker switches, thumb-wheel, infrared port, USB port, and/or a pointerdevice such as a stylus. The one or more buttons (not shown) can includean up/down button for volume control of the speaker 124 and/or themicrophone 126.

The memory interface 102 can be coupled to memory 138. The memory 138can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 138can store operating system instructions 140, such as Darwin, RTXC,LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such asVxWorks. The operating system instructions 140 may include instructionsfor handling basic system services and for performing hardware dependenttasks. In some implementations, the operating system instructions 140can be a kernel (e.g., UNIX kernel).

The memory 138 may include graphical user interface instructions 144 tofacilitate graphic user interface processing; sensor processinginstructions 146 to facilitate sensor-related processing and functions;web browsing instructions 152 to facilitate web browsing-relatedprocesses and functions; media processing instructions 154 to facilitatemedia processing-related processes and functions; GPS/Navigationinstructions 156 to facilitate GPS and navigation-related processes andinstructions; camera instructions 158 to facilitate camera-relatedprocesses and functions; and/or other software instructions 160 tofacilitate other processes and functions (e.g., access controlmanagement functions, etc.). The memory 138 may also store othersoftware instructions (not shown) controlling other processes andfunctions of the mobile device 100 as will be recognized by thoseskilled in the art. In some implementations, the media processinginstructions 154 are divided into audio processing instructions andvideo processing instructions to facilitate audio processing-relatedprocesses and functions and video processing-related processes andfunctions, respectively. An activation record and International MobileEquipment Identity (IMEI) 162 or similar hardware identifier can also bestored in memory 138.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed herein. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 138 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the mobile device 100 may be implemented in hardware and/orin software, including in one or more signal processing and/orapplication specific integrated circuits.

It should be noted that various changes and modifications to thepresently preferred embodiments described herein will be apparent tothose skilled in the art. Such changes and modifications may be madewithout departing from the spirit and scope of the present invention andwithout diminishing its attendant advantages.

I claim:
 1. A mobile device, comprising: a wireless communicationmodule; a processor, controlling the wireless communication module; anda memory controlled by the processor, the memory including instructionsthat when executed by the processor cause the processor to perform thesteps of: providing a graphical user interface through which a usercustomizes one or more functions of the mobile device when placed in aninactive mode; receiving a user selection to automatically initiate theinactive mode in response to the pairing of the mobile device with avehicle; receiving a user selection of an away message to use when themobile device is in inactive mode; in response to the pairing of themobile device and the vehicle, automatically initiating a process toplace the mobile device in inactive mode; when the mobile device is ininactive mode, in response to receiving a communication from thewireless communication module, transmitting the user selected awaymessage via the wireless module and suppressing one or more sound,visual, or vibration communication cues that would have accompanied thecommunication had the mobile device not been in inactive mode.
 2. Themobile device of claim 1 wherein the memory further includesinstructions that when executed by the processor cause it to perform thestep of: when the mobile device is in inactive mode, in response toreceiving the communication from the wireless communication module,suppressing all sound, visual, and vibration communication cues thatwould have accompanied the communication had the mobile device not beenin inactive mode.
 3. The mobile device of claim 1 wherein the memoryfurther includes instructions that when executed by the processor causeit to perform the step of: providing a notification of thecommunications upon completion of the inactive mode.
 4. The mobiledevice of claim 1 wherein the communication received from the wirelesscommunication module is an SMS message.
 5. The mobile device of claim 1wherein the communication received from the wireless communicationmodule is an email.
 6. The mobile device of claim 1 wherein thecommunication received from the wireless communication module is acellular phone call.
 7. The mobile device of claim 1 wherein the userselected away message is a user customized away message.
 8. The mobiledevice of claim 1 wherein the memory further includes instructions thatwhen executed by the processor cause it to perform the step of: when themobile device is placed in inactive mode, provide a notification to acertification server that the mobile device is in inactive mode.
 9. Themobile device of claim 8 wherein the memory further includesinstructions that when executed by the processor cause it to perform thestep of: when the mobile device exits inactive mode, provide anotification to a certification server that the mobile device exitedinactive mode.